Method for spooling experimental data

ABSTRACT

Methods and system for efficient collection and storage of experimental data allow experimental data from high-throughput, feature-rich data collection systems, such as high-throughput cell data collection systems to be efficiently collected, stored, managed and displayed. The methods and system can be used, for example, for storing, managing, and displaying cell image data and cell feature data collected from microplates including multiple wells and a variety of bio-chips in which an experimental compound has been applied to a population of cells. The methods and system provide a flexible and scalable repository of experimental data including multiple databases at multiple locations including pass-through databases that can be easily managed and allows cell data to be analyzed, manipulated and archived. The methods and system may improve the identification, selection, validation and screening of new drug compounds that have been applied to populations of cells.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application a divisional of U.S. application Ser. No. 10/649,323,filed on Aug. 27, 2003, which is a continuation of U.S. application Ser.No. 09/437,976, filed Nov. 10, 1999, abandoned, which claims the benefitof U.S. Provisional Application Nos. 60/108,291, filed on Nov. 13, 1998;60/110,643, filed on Dec. 1, 1998; 60/140,240, filed on Jun. 21, 1999;60/142,375, filed on Jul. 6, 1999; and 60/142,646 filed on Jul. 6, 1999,which applications are incorporated herein by specific reference.

FIELD OF THE INVENTION

This invention relates to collecting and storing experimental data. Morespecifically, it relates to methods and system for efficient collectionand storage of experimental data from automated feature-rich,high-throughput experimental data collection systems.

BACKGROUND OF THE INVENTION

Historically, the discovery and development of new drugs has been anexpensive, time consuming and inefficient process. With estimated costsof bringing a single drug to market requiring an investment ofapproximately 8 to 12 years and approximately $350 to $500 million, thepharmaceutical research and development market is in need of newtechnologies that can streamline the drug discovery process. Companiesin the pharmaceutical research and development market are under fiercepressure to shorten research and development cycles for developing newdrugs, while at the same time, novel drug discovery screeninginstrumentation technologies are being deployed, producing a huge amountof experimental data.

Innovations in automated screening systems for biological and otherresearch are capable of generating enormous amounts of data. The massivevolumes of feature-rich data being generated by these systems and theeffective management and use of information from the data has created anumber of very challenging problems. As is known in the art,“feature-rich” data includes data wherein one or more individualfeatures of an object of interest (e.g., a cell) can be collected. Tofully exploit the potential of data from high-volume data generatingscreening instrumentation, there is a need for new informatic andbioinformatic tools.

Identification, selection, validation and screening of new drugcompounds is often completed at a nucleotide level using sequences ofDeoxyribonucleic Acid (“DNA”), Ribonucleic Acid (“RNA”) or othernucleotides. “Genes” are regions of DNA, and “proteins” are the productsof genes. The existence and concentration of protein molecules typicallyhelp determine if a gene is “expressed” or “repressed” in a givensituation. Responses of genes to natural and artificial compounds aretypically used to improve existing drugs, and develop new drugs.However, it is often more appropriate to determine the effect of a newcompound on a cellular level instead of a nucleotide level.

Cells are the basic units of life and integrate information from DNA,RNA, proteins, metabolites, ions and other cellular components. Newcompounds that may look promising at a nucleotide level may be toxic ata cellular level. Florescence-based reagents can be applied to cells todetermine ion concentrations, membrane potentials, enzyme activities,gene expression, as well as the presence of metabolites, proteins,lipids, carbohydrates, and other cellular components.

There are two types of cell screening methods that are typically used:(1) fixed cell screening; and (2) live cell screening. For fixed cellscreening, initially living cells are treated with experimentalcompounds being tested. No environmental control of the cells isprovided after application of a desired compound and the cells may dieduring screening. Live cell screening requires environmental control ofthe cells (e.g., temperature, humidity, gases, etc.) after applicationof a desired compound, and the cells are kept alive during screening.Fixed cell assays allow spatial measurements to be obtained, but only atone point in time. Live cell assays allow both spatial and temporalmeasurements to be obtained.

The spatial and temporal frequency of chemical and molecular informationpresent within cells makes it possible to extract feature-rich cellinformation from populations of cells. For example, multiple molecularand biochemical interactions, cell kinetics, changes in sub-cellulardistributions, changes in cellular morphology, changes in individualcell subtypes in mixed populations, changes and sub-cellular molecularactivity, changes in cell communication, and other types of cellinformation can be obtained.

The types of biochemical and molecular cell-based assays now accessiblethrough fluorescence-based reagents is expanding rapidly. The need forautomatically extracting additional information from a growing list ofcell-based assays has allowed automated platforms for feature-rich assayscreening of cells to be developed. For example, the ArrayScan System byCellomics, Inc. of Pittsburgh, Pa., is one such feature-richcen•screening system. Cell based systems such as FLIPR, by MolecularDevices, Inc. of Sunnyvale, Calif., FMAT, of PE Biosystems of FosterCity, Calif., ViewLux by EG&G Wallac, now a subsidiary of Perkin-ElmerLife Sciences of Gaithersburg, Md., and others also generate largeamounts of data and photographic images that would benefit fromefficient data management solutions. Photographic images are typicallycollected using a digital camera. A single photographic image may takeup as much as 512 Kilobytes (“KB”) or more of storage space as isexplained below. Collecting and storing a large number of photographicimages adds to the data problems encountered when using high throughputsystems. For more information on fluorescence based systems, see “Brightideas for high-throughput screening—One-step fluorescence HTS assays aregetting faster, cheaper, smaller and more sensitive,” by Randy Wedin,Modern Drug Discovery, Vol. 2(3), pp. 61-71, May/June 1999.

Such automated feature-rich cell screening systems and other systemsknown in the art typically include microplate scanning hardware,fluorescence excitation of cells, fluorescence captive emission optics,a photographic microscopic with a camera, data collection, data storageand data display capabilities. For more information on feature-rich cellscreening see “High Content Fluorescence-Based Screening,” by Kenneth A.Guiliano, et al., Journal of Biomolecular Screening, Vol. 2, No. 4, pp.249-259, Winter 1997, ISSN 1087-0571, “PTH Receptor Internalization,”Bruce R. Conway, et al., Journal of Biomolecular Screening, Vol. 4, No.2, pp. 75-68, April 1999, ISSN 1087-0571, “Fluorescent-ProteinBiosensors: New Tools For Drug Discovery,” Kenneth A. Giuliano and D.Lansing Taylor, Trends in Biotechnology, (“TIBTECH”), Vol. 16, No. 3,pp. 99-146, March 1998, ISSN 0167-7799, all of which are incorporated byreference.

An automated feature-rich cell screening system typically automaticallyscans a microplate plate with multiple wells and acquires multi-colorfluorescence data of cells at one or more instances of time at apre-determined spatial resolution. Automated feature-rich cell screensystems typically support multiple channels of fluorescence to collectmulti-color fluorescence data at different wavelengths and may alsoprovide the ability to collect cell feature information on acell-by-cell basis including such features as the size and shape ofcells and sub-cellar measurements of organelles within a cell.

The collection of data from high throughput screening systems typicallyproduces a very large quantity of data and presents a number ofbioinformatics problems. As is known in the art, “bioinformatic”techniques are used to address problems related to the collection,processing, storage, retrieval and analysis of biological informationincluding cellular information. Bioinformatics is defined as thesystematic development and application of information technologies anddata processing techniques for collecting, analyzing and displaying dataobtained by experiments, modeling, database searching, andinstrumentation to make observations about biological processes.

The need for efficient data management is not limited to feature-richcell screening systems or to cell based arrays. Virtually any instrumentthat runs High Throughput Screening (“RTS”) assays also generate largeamounts of data. For example, with the growing use of other datacollection techniques such as DNA arrays, bio-chips, microscopy,micro-arrays, gel analysis, the amount of data collected, includingphotographic image data is also growing exponentially. As is known inthe art, a “bio-chip” is a stratum with hundreds or thousands ofabsorbent micro-gels fixed to its surface. A single bio-chip may contain10,000 or more micro-gels. When performing an assay test, each micro-gelon a bio-chip is like a micro-test tube or a well in a microplate. Abio-chip provides a medium for analyzing known and unknown biological(e.g., nucleotides, cells, etc.) samples in an automated,high-throughput screening system.

Although a wide variety of data collection techniques can be used,cell-based high throughput screening systems are used as an example toillustrate some of the associated data management problems encounteredby virtually all high throughput screening systems. One problem withcollecting feature-rich cell data is that a microplate plate used forfeature-rich screening typically includes 96 to 1536 individual wells.As is known in the art, a “microplate” is a flat, shallow dish thatstores multiple samples for analysis. A “well” is a small area in amicroplate used to contain an individual sample for analysis. Each wellmay be divided into multiple fields. A “field” is a sub-region of a wellthat represents a field of vision (i.e., a zoom level) for aphotographic microscope. Each well is typically divided into one tosixteen fields. Each field typically will have between one and sixphotographic images taken of it, each using a different light filter tocapture a different wavelength of light for a different fluorescenceresponse for desired cell components. In each field, a pre-determinednumber of cells are selected to analyze. The number of cells will vary(e.g., between ten and one hundred). For each cell, multiple cellfeatures are collected. The cell features may include features such assize, shape, etc. of a cell. Thus, a very large amount of data istypically collected for just one well on a single microplate.

From a data volume perspective, the data to be saved for a well can beestimated by number of cell feature records collected and the number ofimages collected. The number of images collected can be typicallyestimated by: (number of wells×number of fields×images per field). Thecurrent size of an image file is approximately 512 Kilobytes (“KB”) ofuncompressed data. As is known in the art, a byte is 8-bits of data. Thenumber of cell feature records can typically be estimated by: (number ofwells×number of fields×cells per field×features per cell). Datacollected from multiple wells on a microplate is typically formatted andstored on a computer system. The collected data is stored in format thatcan be used for visual presentation software, and allow for data miningand archiving using bioinformatic techniques.

For example, in a typical scenario, scanning one low density microplatewith 96 wells, using four fields per well, three images per field and animage size of 512 Kbytes per image, generates about 1,152 images andabout 576 megabytes (“MB”) of image data (i.e., (96×4×3×512×(1 KB=1024bytes)/(1 MB=(1024 bytes×1024 bytes))=576 MB). As is known in the art, amegabyte is 220 or 1,048,576 bytes and is commonly interpreted as “onemillion bytes.”

If one hundred cells per field are selected with ten features per cellcalculated, such a scan also generates (96×4×100×10)=288,000 cellfeature records, whose data size varies with the amount of cell featurescollected. This results in about 12,000 MB of data being generated perday and about 60,000 MB per week, scanning the 96 well microplatestwenty hours a day, five days a week.

In a high data volume scenario based on a current generation offeature-rich cell screening systems, scanning one high-densitymicroplate with 384 wells, using sixteen fields per well, four imagesper field, 100 cells per field, ten features per cell, and 512 KB perimage, generates about 24,576 images or about 12,288 MB of image dataand about 6,144,000 cell feature records. This results in about 14,400MB of data being generated per day and about 100,800 MB per week,scanning the 384 well microplates twenty-four hours a day, seven days aweek.

Since multiple microplates can be scanned in parallel, and multipleautomated feature-rich cell screening systems can operate 24 hours aday, seven days a week, and 365 days a year, the experimental datacollected may easily exceed physical storage limits for a typicalcomputer network. For example, disk storage on a typical computernetwork may be in the range from about ten gigabytes (“GB”) to aboutone-hundred GB of data storage. As is known in the art, a gigabyte is230 bytes, or 1024 MB and is commonly interpreted as “one billionbytes.”

The data storage requirements for using automated feature-rich cellscreening on a conventional computer network used on a continuous basiscould easily exceed a terabyte (“TB”) of storage space, which isextremely expensive based on current data storage technologies. As isknown in the art, one terabyte equals 240 bytes, and is commonlyinterpreted as “one trillion bytes.” Thus, collecting and storing datafrom an automated feature-rich cell screening system may severely impactthe operation and storage of a conventional computer network.

Another problem with feature-rich cell screening systems is even thougha massive amount of cell data is collected, only a very small percentageof the total cell feature data and image data collected will ever beused for direct visual display. Nevertheless, to gather statisticallyrelevant information about a new compound all of the cell datagenerated, is typically stored on a local hard disk and available foranalysis. This may also severely impact a local hard disk storage.

Yet another problem is that microplate scan results information for onemicroplate can easily exceed about 1,000 database records per plate, andcell feature data and image data can easily exceed about 6,000,000database records per plate. Most conventional databases used on personalcomputers can not easily store and manipulate such a large number ofdata records. In addition, waiting relatively long periods of time toopen such a large database on a conventional computer personal computerto query and/or display data may severely affect the performance of anetwork and may quickly lead to user frustration or userdissatisfaction.

Thus, it is desirable to provide a data storage system that can be usedfor feature-rich screening on a continuous basis. The data storagesystem should provide a flexible and scalable repository of cell datathat can be easily managed and allows data to be analyzed, manipulatedand archived.

SUMMARY OF THE INVENTION

In accordance with preferred embodiments of the present invention, someof the problems associated with collecting and storing feature-richexperimental data are overcome. Methods and system for efficientcollection and storage of experimental data is provided. One aspect ofthe present invention includes a method for collecting experimentaldata. The method includes collecting image and feature data from desiredsub-containers within a container. The image and feature data is storedin multiple image and feature databases. Summary data calculated for thedesired sub-containers and the container are stored in sub-container andcontainer databases.

Another aspect of the present invention includes a method for storingexperimental data on a computer system. The method includes collectingimage data and feature data from desired sub-containers in a container.The image and feature data is stored in multiple third databasescomprising multiple database tables. Summary data calculated for desiredsub-containers and the container is stored in a second databasecomprising multiple database tables. A first database is created that isa “pass-through” database. The first database includes a pass-throughdatabase table with links to the second database and links to themultiple third databases, but does not include any data collected fromthe container.

Another aspect of the present invention includes a method for spoolingexperimental data off devices that collect the data to a number ofdifferent remote storage locations. Links in a pass-through databasetable in a first database are updated to reflect the new locations ofsecond database and multiple third databases.

Another aspect of the present invention includes a method forhierarchical management of experimental data. A pre-determined storageremoval policy is applied to database files in a database. If anydatabase files match the pre-determined storage removal policy, thedatabase files are copied into a layer in a multi-layered hierarchicalstorage management system. The original database files are replaced withplaceholder files that include a link to the original database files inthe layer in the hierarchical storage management system.

Another aspect of the invention includes presenting the experimentaldata from a display application on a computer. The data presented by thedisplay application is obtained from multiple databases obtained frommultiple locations remote to the computer. The data displayed appears tobe obtained from databases on local storage on the computer instead offrom the remote locations.

Another aspect of the invention includes a data storage system thatprovides virtually unlimited amounts of “virtual” disk space for datastorage at multiple local and remote storage locations for storingexperimental data that is collected.

These methods and system may allow experimental data fromhigh-throughput data collection systems to be efficiently collected,stored, managed and displayed. For example, the methods and system canbe used for, but is not limited to, storing managing and displaying cellimage data and cell feature data collected from microplates includingmultiple wells or bio-chips including multiple micro-gels in which anexperimental compound has been applied to a population of cells.

The methods and system may provide a flexible and scalable repository ofexperimental data that can be easily managed and allows the data to beanalyzed, manipulated and archived. The methods and system may improvethe identification, selection, validation and screening of newexperimental compounds (e.g., drug compounds). The methods and systemmay also be used to provide new bioinformatic techniques used to makeobservations about experimental data.

The foregoing and other features and advantages of preferred embodimentsof the present invention will be more readily apparent from thefollowing detailed description. The detailed description proceeds withreferences to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments of the present invention are described withreference to the following drawings, wherein:

FIG. 1A is a block diagram illustrating an exemplary experimental datastorage system;

FIG. 1B is a block diagram illustrating an exemplary experimental datastorage system;

FIG. 2 is a block diagram illustrating an exemplary array scan modulearchitecture;

FIGS. 3A and 3B are a flow diagram illustrating a method for collectingexperimental data;

FIG. 4 is a flow diagram illustrating a method for storing experimentaldata;

FIG. 5 is a block diagram illustrating an exemplary database system forthe method of FIG. 4;

FIG. 6 is a block diagram illustrating an exemplary database tablelayout in an application database of FIG. 5;

FIG. 7 is a block diagram illustrating an exemplary database tables in asystem database of FIG. 5;

FIG. 8 is a block diagram illustrating an exemplary database tables inan image and feature database of FIG. 5;

FIG. 9 is a flow diagram illustrating a method for spooling experimentaldata;

FIG. 10 is a flow diagram illustrating a method for hierarchicalmanagement experimental data;

FIG. 11 is a flow diagram illustrating a method for presentingexperimental data; and

FIG. 12 is a block diagram illustrating a screen display for graphicallydisplaying experimental data.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS Exemplary Data StorageSystem

FIG. 1A illustrates an exemplary data storage system 10 for preferredembodiments of the present invention. The exemplary data storage system10 includes an analysis instrument 12, connected to a client computer18, a shared database 24 and a data store archive 30 with a computernetwork 40. The analysis instrument 12 includes any scanning instrumentcapable of collecting feature-rich experimental data, such asnucleotide, cell or other experimental data, or any analysis instrumentcapable of analyzing feature-rich experimental data. As is known in theart, “feature-rich” data includes data wherein one or more individualfeatures of an object of interest (e.g., a cell) can be collected. Theclient computer 18 is any conventional computer including a displayapplication that is used to lead a scientist or lab technician throughdata analysis. The shared database 24 is a multi-user, multi-viewrelational database that stores data from the analysis instrument 12.The data archive 30 is used to provide virtually unlimited amounts of“virtual” disk space with a multi-layer hierarchical storage managementsystem. The computer network 40 is any fast Local Area Network (“LAN”)(e.g., capable of data rates of 100 Mega-bit per second or faster).However, the present invention is not limited to this embodiment andmore or fewer, and equivalent types of components can also be used. Datastorage system 10 can be used for virtually any system capable ofcollecting and/or analyzing feature-rich experimental data frombiological and non-biological experiments.

FIG. 1B illustrates an exemplary data storage system 10′ for onepreferred embodiment of the present invention with specific components.However, the present invention is not limited to this one preferredembodiment, and more or fewer, and equivalent types of components canalso be used. The data storage system 10′ includes one or more analysisinstruments 12, 14, 16, for collecting and/or analyzing feature-richexperimental data, one or more data store client computers, 18, 20, 22,a shared database 24, a data store server 26, and a shared database fileserver 28. A data store archive 30 includes any of a disk archive 32, anoptical jukebox 34 or a tape drive 36. The data store archive 30 can beused to provide virtually unlimited amounts of “virtual” disk space witha multi-layer hierarchical storage management system without changingthe design of any databases used to stored collected experimental dataas is explained below. The data store archive 30 can be managed by anoptional data archive server 38. Data storage system 10′ components areconnected by a computer network 40. However, more or fewer data storecomponents can also be used and the present invention is not limited tothe data storage system 10′ components illustrated in FIG. 1B.

In one exemplary preferred embodiment of the present invention, datastorage system 10′ includes the following specific components. However,the present invention is not limited to these specific components andother similar or equivalent components may also be used. Analysisinstruments 12, 14, 16, comprise a feature-rich array scanning systemcapable of collecting and/or analyzing experimental data such as cellexperimental data from microplates, DNA arrays or other chip-based orbio-chip based arrays. Bio-chips include any of those provided byMotorola Corporation of Schaumburg, Ill., Packard Instrument, asubsidiary of Packard BioScience Co. of Meriden, Conn., Genometrix, Inc.of Woodlands, Tex., and others.

Analysis instruments 12, 14, 16 include any of those provided byCellomics, Inc. of Pittsburgh, Pa., Aurora Biosciences Corporation ofSan Diego, Calif., Molecular Devices, Inc. of Sunnyvale, Calif., PEBiosystems of Foster City, Calif., Perkin-Elmer Life Sciences ofGaithersburg, Md., and others. The one or more data store clientcomputers, 18, 20, 22, are conventional personal computers that includea display application that provides a Graphical User Interface (“GUI”)to a local hard disk, the shared database 24, the data store server 26and/or the data store archive 30. The Gill display application is usedto lead a scientist or lab technician through standard analyses, andsupports custom and query viewing capabilities. The display applicationGill also supports data exported into standard desktop tools such asspreadsheets, graphics packages, and word processors.

The data store client computers 18, 20, 22 connect to the store server26 through an Open Data Base Connectivity (“ODBC”) connection overnetwork 40. In one embodiment of the present invention, computer network40 is a 100 Mega-bit (“Mbit”) per second or faster Ethernet, Local AreaNetwork (“LAN”). However, other types of LANs could also be used (e.g.,optical or coaxial cable networks). In addition, the present inventionis not limited to these specific components and other similar componentsmay also be used.

As is known in the art, OBDC is an interface providing a common languagefor applications to gain access to databases on a computer network. Thestore server 26 controls the storage based functions plus an underlyingDatabase Management System (“DBMS”).

The shared database 24 is a multi-user, multi-view relational databasethat stores summary data from the one or more analysis instruments 12,14, 16. The shared database 24 uses standard relational database toolsand structures. The data store archive 30 is a library of image andfeature database files. The data store archive 30 uses HierarchicalStorage Management (“HSM”) techniques to automatically manage disk spaceof analysis instruments 12, 14, 16 and the provide a multi-layerhierarchical storage management system. The HSM techniques are explainedbelow.

An operating environment for components of the data storage system 10and 10′ for preferred embodiments of the present invention include aprocessing system with one or more high-speed Central ProcessingUnite(s) (“CPU”) and a memory. In accordance with the practices ofpersons skilled in the art of computer programming, the presentinvention is described below with reference to acts and symbolicrepresentations of operations or instructions that are performed by theprocessing system, unless indicated otherwise. Such acts and operationsor instructions are referred to as being “computer-executed” or “CPUexecuted.”

It will be appreciated that acts and symbolically represented operationsor instructions include the manipulation of electrical signals by theCPU. An electrical system represents data bits which cause a resultingtransformation or reduction of the electrical signals, and themaintenance of data bits at memory locations in a memory system tothereby reconfigure or otherwise alter the CPUs operation, as well asother processing of signals. The memory locations where data bits aremaintained are physical locations that have particular electrical,magnetic, optical, or organic properties corresponding to the data bits.

The data bits may also be maintained on a computer readable mediumincluding magnetic disks, optical disks, organic memory, and any othervolatile (e.g., Random Access Memory (“RAM”)) or non-volatile (e.g.,Read-Only Memory (“ROM”)) mass storage system readable by the CPU. Thecomputer readable medium includes cooperating or interconnected computerreadable medium, which exist exclusively on the processing system or bedistributed among multiple interconnected processing systems that may belocal or remote to the processing system.

Array Scan Module Architecture

FIG. 2 is a block diagram illustrating an exemplary array scan module 42architecture. The array scan module 42, such as one associated withanalysis instrument 12, 14, 16 (FIG. 1B) includes software/hardware thatis divided into four functional groups or modules. However, more offewer functional modules can also be used and the present invention isnot limited to four functional modules. The Acquisition Module 44controls a robotic microscope and digital camera, acquires images andsends the images to the Assay Module 46. The Assay Module 46 “reads” theimages, creates graphic overlays, interprets the images collects featuredata and returns the new images and feature data extracted from theimages back to the Acquisition Module 44. The Acquisition Module 44passes the image and interpreted feature data to the Data Base StorageModule 48. The Data Base Storage Module 48 saves the image and featureinformation in a combination of image files and relational databaserecords. The store clients 18, 20, 22 use the Data Base Storage Module48 to access feature data and images for presentation and data analysisby the Presentation Module 50. The Presentation Module 50 includes adisplay application with a Gill as was discussed above.

Collection of Experimental Data

FIGS. 3A and 3B are a flow diagram illustrating a Method 52 forcollecting experimental data. In FIG. 3A at Step 54, a container withmultiple sub-containers is initialized using configuration information.At Step 56, the configuration information used for the container isstored in a container database. At Step 58, a loop is entered to repeatSteps 60, 62, 64, 66, 68, 70 and 72 for desired sub-containers in thecontainer. At Step 60, a sub-container in the container is selected. Ina preferred embodiment of the present invention, all of thesub-containers in a container are analyzed. In another embodiment of thepresent invention, less than all of the sub-containers in a containerare analyzed. In such an embodiment, a user can select a desired sub-setof the sub containers in a container for analysis. At Step 62, imagedata is collected from the sub container. At Step 64, the image data isstored in an image database. At Step 66, feature data is collected fromthe image data.

In FIG. 3B at Step 68, the feature data is stored in a feature database.In one embodiment of the present invention, the image database andfeature databases are combined into a single database comprisingmultiple tables including the image and feature data. In anotherembodiment of the present invention, the image database and featuredatabases are maintained as separate databases.

At Step 70, sub-container summary data is calculated. At Step 72, thesub-container summary data is stored in a sub-container database. In oneembodiment of the present invention, the sub-container database and thecontainer database are combined into a single database comprisingmultiple tables including the sub-container and container summary data.In another embodiment of the present invention, the sub-container andcontainer databases are maintained as separate databases. The loopcontinues at Step 58 (FIG. 3A) until the desired sub-containers within acontainer have been analyzed. After the desired sub-containers have beenprocessed in the container, the loop at Step 58 ends.

At Step 74 of FIG. 3B, container summary data is calculated usingsub-container summary data from the sub-container database. At Step 76,the container summary data is stored in the container database.

In a general use of the invention, at Step 66 features from anyimaging-based analysis system can be used. Given a digitized imageincluding one or more objects (e.g., cells), there are typically twophases to analyzing an image and extracting feature data as featuremeasurements. The first phase is typically called “image segmentation”or “object isolation,” in which a desired object is isolated from therest of the image. The second phase is typically called “featureextraction,” wherein measurements of the objects are calculated. A“feature” is typically a function of one or more measurements,calculated so that it quantifies a significant characteristic of anobject. Typical object measurements include size, shape, intensity,texture, location, and others.

For each measurement, several features are commonly used to reflect themeasurement. The “size” of an object can be represented by its area,perimeter, boundary definition, length, width, etc. The “shape” of anobject can be represented by its rectangularity (e.g., length and widthaspect ratio), circularity (e.g., perimeter squared divided by area,bounding box, etc.), moment of inertia, differential chain code, Fourierdescriptors, etc. The “intensity” of an object can be represented by asummed average, maximum or minimum grey levels of pixels in an object,etc. The “texture” of an object quantifies a characteristic ofgrey-level variation within an object and can be represented bystatistical features including standard deviation, variance, skewness,kurtosis and by spectral and structural features, etc. The “location” ofan object can be represented by an object's center of mass, horizontaland vertical extents, etc. with respect to a pre-determined grid system.For more information on digital image feature measurements, see:“Digital Image Processing,” by Kenneth R. Castleman, Prentice-Hall,1996, ISBN-0132114674, “Digital Image Processing: Principles andApplications,” by G. A. Baxes, Wiley, 1994, ISBN-0471 009490, “DigitalImage Processing,” by William K. Pratt, Wiley and Sons, 1991,ISBN-0471857661, or “The Image Processing Handbook—2nd Edition,” by JohnC. Russ, CRC Press, 1991, ISBN-0849325 161, the contents of all of whichare incorporated by reference.

In one exemplary preferred embodiment of the present invention, Method52 is used to collect cell image data and cell feature data from wellsin a “microplate.” In another preferred embodiment of the presentinvention, Method 52 is used to collect cell image and cell feature datafrom micro-gels in a bio-chip. As is known in the art, a “microplate” isa flat, shallow dish that stores multiple samples for analysis andtypically includes 96 to 1536 individual wells. A “well” is a small areain a microplate used to contain an individual sample for analysis. Eachwell may be divided into multiple fields. A “field” is a sub-region of awell that represents a field of vision (i.e., a zoom level) for aphotographic microscope. Each well is typically divided into one tosixteen fields. Each field typically will have between one and sixphotographic images taken of it, each using a different light filter tocapture a different wavelength of light for a different fluorescenceresponse for desired cell components. However, the present invention isnot limited to such an embodiment, and other containers (e.g., varietiesof biological chips, such as DNA chips, micro-arrays, and othercontainers with multiple sub-containers), sub-containers can also beused to collect image data and feature data from other than cells.

In an embodiment collecting cell data from wells in a microplate, atStep 54 a microplate with multiple wells is initialized usingconfiguration information. At Step 56, the configuration informationused for the microplate is stored in a microplate database. At Step 58,a loop is entered to repeat Steps 60, 62, 64, 66, 68, 70 and 72 fordesired wells in the microplate. At Step 60, a well in the microplate isselected. At Step 62, cell image data is collected from the well. In onepreferred embodiment of the present invention, the cell image dataincludes digital photographic images collected with a digital cameraattached to a robotic microscope. However, other types of cameras canalso be used and other types of image data can also be collected. AtStep 64, the cell image data is stored in an image database. In anotherexemplary preferred embodiment of the present invention, the imagedatabase is a collection of individual image files stored in a binaryformat (e.g., Tagged Image File Format (“TIFF”), Device-Independent Bitmap (“DIB”) and others). The collection of individual image files mayormay not be included in a formal database framework. The individual imagefiles may exist as a collection of individual image files in specifieddirectories that can be accessed from another database (e.g., apass-through database).

At Step 66, cell feature data is collected from the cell image data. Inone preferred embodiment of the present invention, Step 66 includescollecting any of the cell feature data illustrated in Table 1. However,other feature data and other cell feature can also be collected and thepresent invention is not limited to the cell feature data illustrated inTable 1. Virtually any feature data can be collected from the imagedata.

TABLE 1 CELL SIZE CELL SHAPE CELL INTENSITY CELL TEXTURE CELL LOCATIONCELL AREA CELL PERIMETER CELL SHAPE FACTOR CELL EQUIVALENT DIAMETER CELLLENGTH CELL WIDTH CELL INTEGRATED FLUORESCENCE INTENSITY CELL MEANFLUORESCENCE INTENSITY CELL VARIANCE CELL SKEWNESS CELL KURTOSIS CELLMINIMUM FLUORESCENCE INTENSITY CELL MAXIMUM FLUORESCENCE INTENSITY CELLGEOMETRIC CENTER. CELL X-COORDINATE OF A GEOMETRIC CENTER CELLY-COORDINATE OF A GEOMETRIC CENTER

In FIG. 3B at Step 68, the cell feature data is stored in a cell featuredatabase. In one embodiment of the present invention, the image databaseand cell feature databases are combined into a single databasecomprising multiple tables including the cell image and cell featuredata. In another embodiment of the present invention, the image database(or image files) and feature databases are maintained as separatedatabases.

Returning to FIG. 3B at Step 70, well summary data is calculated usingthe image data and the feature data collected from the well. In onepreferred embodiment of the present invention, the well summary datacalculated at Step 72 includes calculating any of the well summary dataillustrated in Table 2. However, the present invention is not limited tothe well summary data illustrated in Table 2, and the othersub-containers and other sub-container summary data can also becalculated. Virtually any sub-container summary data can be calculatedfor desired sub-containers. In Table 2, a “SPOT” indicates a block offluorescent response intensity as a measure of biological activity.

TABLE 2 WELL CELL SIZES WELL CELL SHAPES WELL CELL INTENSITIES WELL CELLTEXTURES WELL CELL LOCATIONS WELL NUCLEUS AREA WELL SPOT COUNT WELLAGGREGATE SPOT AREA WELL AVERAGE SPOT AREA WELL MINIMUM SPOT AREA WELLMAXIMUM SPOT AREA WELL AGGREGATE SPOT INTENSITY WELL AVERAGE SPOTINTENSITY WELL MINIMUM SPOT INTENSITY WELL MAXIMUM SPOT INTENSITY WELLNORMALIZED AVERAGE SPOT INTENSITY WELL NORMALIZED SPOT COUNT WELL NUMBEROF NUCLEI WELL NUCLEUS AGGREGATE INTENSITY WELL DYE AREA WELL DYEAGGREGATE INTENSITY WELL NUCLEUS INTENSITY WELL CYTOPLASM INTENSITY WELLDIFFERENCE BETWEEN NUCLEUS AND CYTOPLASM INTENSITY WELL NUCLEUS BOX-FILLRATIO WELL NUCLEUS PERIMETER SQUARED AREA WELL NUCLEUS HEIGHT/WIDTHRATIO WELL CELL COUNT

Returning to FIG. 3B at Step 72, the well summary data is stored in awell database. In one embodiment of the present invention, the welldatabase and the microplate database are combined into a single databasecomprising multiple tables including the well and microplate data. Inanother embodiment of the present invention, the well and microplatedatabases are maintained as separate databases. Returning to FIG. 3A,the loop continues at Step 58 (FIG. 3A) until the desired sub-wellswithin a microplate have been analyzed.

After the desired wells have been processed in the microplate, the loopat Step 58 ends. At Step 74 of FIG. 3B, summary data is calculated usingwell summary data from the microplate database. At Step 76, themicroplate summary data is stored in the well database.

In one preferred embodiment of the present invention, the microplatesummary data calculated at Step 74 includes calculating any of themicroplate summary data illustrated in Table 3. However, the presentinvention is not limited to the microplate summary data illustrated inTable 3, and other container and other container summary data can alsobe calculated. Virtually any container summary data can be calculatedfor a container. In Table 3, “MEAN” indicates a statistical mean and“STDEV” indicates a statistical standard deviation, known in the art,and a “SPOT” indicates a block of fluorescent response intensity as ameasure of biological activity.

TABLE 3 MEAN SIZE OF CELLS MEAN SHAPES OF CELLS MEAN INTENSITY OF CELLSMEAN TEXTURE OF CELLS LOCATION OF CELLS NUMBER OF CELLS NUMBER OF VALIDFIELDS STDEV NUCLEUS AREA MEAN SPOT COUNT STDEV SPOT COUNT MEANAGGREGATE SPOT AREA STDEV AGGREGATE SPOT AREA MEAN AVERAGE SPOT AREASTDEV AVERAGE SPOT AREA MEAN NUCLEUS AREA MEAN NUCLEUS AGGREGATEINTENSITY STDEV AGGREGATE NUCLEUS INTENSITY MEAN DYE AREA STDEV DYE AREAMEAN DYE AGGREGATE INTENSITY STDEV AGGREGATE DYE INTENSITY MEAN MINIMUMSPOT AREA STDEV MINIMUM SPOT AREA MEAN MAXIMUM SPOT AREA STDEV MAXIMUMSPOT AREA MEAN AGGREGATE SPOT INTENSITY STDEV AGGREGATE SPOT INTENSITYMEAN AVERAGE SPOT INTENSITY STDEV AVERAGE SPOT INTENSITY MEAN MINIMUMSPOT INTENSITY STDEV MINIMUM SPOT INTENSITY MEAN MAXIMUM SPOT INTENSITYSTDEV MAXIMUM SPOT INTENSITY MEAN NORMALIZED AVERAGE SPOT INTENSITYSTDEV NORMALIZED AVERAGE SPOT INTENSITY MEAN NORMALIZED SPOT COUNT STDEVNORMALIZED SPOT COUNT MEAN NUMBER OF NUCLEI STDEV NUMBER OF NUCLEINUCLEI INTENSITIES CYTOPLASM INTENSITIES DIFFERENCE BETWEEN NUCLEI ANDCYTOPLASM INTENSITIES NUCLEI BOX-FILL RATIOS NUCLEI PERIMETER SQUAREDAREAS NUCLEI HEIGHTIWIDTH RATIOS WELL CELL COUNTS

In one exemplary preferred embodiment of the present invention, cellassays are created using selected entries from Tables 1-3. In apreferred embodiment of the present invention, a “cell assay” is aspecific implementation of an image processing method used to analyzeimages and return results related to biological processes beingexamined. For more information on the image processing methods used incell assays targeted to specific biological processes, see co-pendingapplication Ser. Nos. 09/031,217 and 09/352,171, assigned to the sameAssignee as the present application, and incorporated herein byreference.

In one exemplary preferred embodiment of the present invention, themicroplate and well databases are stored in a single database comprisingmultiple tables called “SYSTEM.MDB.” The image and feature data for eachwell is stored in separate databases in the format “ID.MDB,” where ID isa unique identifier for a particular scan. However, the presentinvention is not limited to this implementation, and other types, andmore or fewer databases can also be used.

Storing Experimental Data

FIG. 4 is a flow diagram illustrating a Method 78 for storing collectedexperimental data. At Step 80, image data and feature data is collectedfrom desired sub-containers in a container (e.g., with Method 52 of FIG.3). At Step 82, a first database is created. The first database includeslinks to other databases but does not include any data collected fromthe container. The first database is used as a “pass-through” databaseby a display application to view data collected from a container. AtStep 84, a first entry is created in the first database linking thefirst database to a second database. The second database includesconfiguration data used to collect data from the container, summary datafor the container calculated from the desired sub-containers and summarydata for the desired sub-containers in the container calculated from theimage data and feature data. The information is organized in multipledatabase tables in the second database. At Step 86, multiple secondentries are created in the first database linking the first database tomultiple third databases. The multiple third databases include imagedata and feature data collected from the desired sub-containers in thecontainer. The data is organized in multiple database tables in thethird database.

In one exemplary preferred embodiment of the present invention, at Step80, image data and feature data is collected from desired wells in amicroplate using Method 52 of FIG. 3. However, the present invention isnot limited to using Method 52 to collect experimental data and othermethods can also be used. In addition, the present invention is notlimited to collecting image data and feature data from wells in amicroplate and other sub-containers and containers can also be used(e.g., bio-chips with multiple micro-gels).

At Step 82, an application database is created. In one exemplarypreferred embodiment of the present invention, the application databaseincludes links to other databases but does not include any datacollected from the microplate. The application database is used by adisplay application to view data collected from a microplate. In anotherembodiment of the present invention, the application database mayinclude actual data.

FIG. 5 is a block diagram illustrating an exemplary database system 88for Method 78 of FIG. 4. The database system 88 includes an applicationdatabase 90, a system database 92 and multiple image and featuredatabases 94, 96, 98, 100. FIG. 5 illustrates only four image andfeature databases numbered 1-N. However, the present invention is notlimited to four image and features databases and typically hundreds orthousands of individual image and feature databases may actually beused. In addition the present invention is not limited to the databasesor database names illustrated in FIG. 5 and more or fewer databases andother database names may also be used.

In one exemplary preferred embodiment of the present invention, theapplication database 90 is called “APP.MDB.” However, other names canalso be used for the application database in the database system and thepresent invention is not limited to the name described.

In one exemplary preferred embodiment of the present invention, adisplay application used to display and analyze collected experimentaldoes not access over a few thousand records at one time. This is becausethere is no need for evaluation of microplate detail data information(e.g., image or cell feature database data) across microplates. Summarymicroplate information is stored in microplate, well, microplate featureand well feature summary tables to be compared across microplates.Detailed information about individual cells is accessed within thecontext of evaluating one microplate test. This allows a displayapplication to make use of pass-through tables in the applicationdatabase 90.

In a preferred embodiment of the present invention, the applicationdatabase 90 does not contain any actual data, but is used as a“pass-through” database to other databases that do contain actual data.As is known in the art, a pass-through database includes links to otherdatabases, but a pass-through database typically does not contain anyactual database data. In such and embodiment, the application database90 uses links to the system database 92 and the multiple image andfeature databases 94, 96, 98, 100 to pass-through data requests to theapplication database 90 to these databases. In another exemplarypreferred embodiment of the present invention, the application database90 may include some of the actual data collected, or summaries of actualdata collected. In one exemplary preferred embodiment of the presentinvention, the application database 90 is a Microsoft Access database, aMicrosoft Structured Query Language (“SQL”) database or Microsoft SQLServer by Microsoft of Redmond, Wash. However, other databases such asOracle databases by Oracle Corporation of Mountain View, Calif., couldalso be used for application database 90, and the present invention isnot limited to Microsoft databases.

In another preferred embodiment of the present invention, a firstpass-through database is not used at all. In such an embodiment, thefirst pass-through database is replaced by computer software thatdynamically “directs” queries to/from the second and third databaseswithout actually creating or using a first pass-through database.

FIG. 6 is a block diagram illustrating an exemplary database tablelayout 102 for the application database 90 of FIG. 5. The database tablelayout 102 of FIG. 6 includes a first pass-through database entry 104linking the application database 90 to the system database 92. Thedatabase table layout also includes multiple second pass throughdatabase entries 106, 108, 110, 112 linking the application database tomultiple image and feature databases 94, 96, 98, 100. However, more orfewer types of database entries can also be used in the applicationdatabase, and the present invention is not limited to two types ofpass-through databases entries. In another embodiment of the presentinvention, the application database 92 may also include experimentaldata (not illustrated in FIG. 6).

Returning to FIG. 4 at Step 84, a first entry is created in theapplication database 90 linking the application database 90 to a systemdatabase 92 (e.g., box 104, FIG. 6). The system database 92 includesconfiguration data used to collect data from a microplate, summary datafor the microplate calculated from the desired wells and summary datafor selected wells in the microplate calculated from the image data andfeature data. This information is organized in multiple tables in thesystem database 92.

In one exemplary preferred embodiment of the present invention, thesystem database 92 is called “SYSTEM.MDB.” However, other names couldalso be used and the present invention is not limited to this name. Thesystem database 92 may also be linked to other databases includingmicroplate configuration and microplate summary data and is used in apass-through manner as was described above for the application database.In another exemplary preferred embodiment of the present invention, thesystem database 92 is not linked to other databases, but insteadincludes actual microplate configuration and microplate summary data inmultiple internal tables.

However, in either case, in one preferred embodiment of the presentinvention, the name of the system database 92 is not changed frommicroplate-to-microplate. In another preferred embodiment of the presentinvention, the name of the system database 92 is changed frommicroplate-to-microplate. A display application will refer to the systemdatabase 92 using its assigned name (e.g., SYSTEM.MDB) for microplateconfiguration and microplate summary data. Data stored in the systemdatabase 92 may be stored in linked databases so that the actualmicroplate container configuration and microplate summary data can berelocated without changing the display application accessing the systemdatabase 92. In addition the actual database engine could be changed toanother database type, such as a Microsoft SQL Server or Oracledatabases by Oracle, or others without modifying the display applicationaccessing the system database 92.

FIG. 7 is a block diagram illustrating exemplary database tables 114 forthe system database 92 of FIG. 5. The database table, 114 of FIG. 7includes a plate table 116 that includes a list of plates being used.The plate table 116 is linked to a protocol table 118, a form factortable 122, a plate feature table 124 and a well table 126. The protocoltable 118 includes protocol information. In a preferred embodiment ofthe present invention, a protocol specifies a series of system settingsincluding a type of analysis instrument, an assay, dyes used to measurebiological markers cell identification parameters and other parametersused to collect experimental data. An assay is described below. The formfactor table 122 includes microplate layout geometry. For example, astandard 96-well microplate includes 12 columns of wells labeled 1through 12 and 8 rows of wells labeled A through H for a total of 98.The plate feature table 124 includes a mapping of features tomicroplates. The form factor table 122 is liked to the manufacturertable 120. The manufacture table 120 includes a list microplatemanufactures and related microplate information. The well table 126includes details in a well. In a preferred embodiment of the presentinvention, a well is a small area (e.g., a circular area) in amircoplate used to contain cell samples for analysis.

The protocol table 118 is linked to a protocol assay parameters table128. In a preferred embodiment of the present invention, an “assay” is aspecific implementation of an image processing method used to analyzeimages and return results related to biological processes beingexamined. The protocol assay parameters table 128 is linked to an assayparameters table 130. The assay parameters table 130 include parametersfor an assay in use.

The protocol table 118 is also linked to a protocol channel table 132.Typically an assay will have two or more channels. A “channel” is aspecific configuration of optical filters and channel specificparameters and is used to acquire an image. In a typical assay,different fluorescent dyes are used to label different cell structures.The fluorescent dyes emit light at different wavelengths. Channels areused to acquire photographic images for different dye emissionwavelengths. The protocol channel table 132 is linked to a protocolchannel reject parameters table 134. The protocol channel rejectparameters table 134 includes channel parameters used to reject imagesthat do not meet the desired channel parameters.

The protocol table 118 is also linked to a protocol scan area table 136.The protocol scan area table 136 includes methods used to scan a well.The protocol scan area table 136 is linked to a system table 138. Thesystem table 138 includes information configuration information andother information used to collect experimental data.

The well table 126 is linked to a well feature table 140. The wellfeature table 140 includes mapping of cell features to wells. The wellfeature table 140 is linked to a feature type table 142. The featuretype table 142 includes a list of features (e.g., cell features) thatwill be collected. However, more or fewer tables can also be used, moreor fewer links can be used to link the tables, and the present inventionis not limited to the tables described for the system database 92.

Returning to FIG. 4 Step 86, multiple second entries (e.g., boxes 106,108, 110, 112 of FIG. 6) are created in the application database 92linking the application database 92 to multiple image and featuredatabases 94, 96, 98, 100. The multiple image and feature databasesinclude image data and feature data collected from the desired wells inthe microplate. The data is organized in multiple database tables in theimage and feature databases.

In one exemplary preferred embodiment of the present invention, names ofimage and feature databases 94, 96, 98, 100 that contain the actualimage and feature data are changed dynamically frommicroplate-to-microplate. Since the image and feature data will includemany individual databases, an individual image and feature database iscreated when a microplate record is created (e.g., in the plate table116 (FIG. 7) in the system database 92 (FIG. 5)) and has a name that iscreated by taking a plate field value and adding “.MDB” to the end. (Forexample, a record in a plate table 116 with a field identifier of“1234569803220001” will have it's data stored in a image and featuredatabase with the name “1234569803220001.MDB”). However, other names canalso be used for the image and feature databases and the presentinvention is not limited to the naming scheme using a field identifierfrom the plate table 116.

FIG. 8 is a block diagram illustrating exemplary database tables 144 forimage and feature databases 94, 96, 98, 100 of FIG. 5. In one preferredembodiment of the present invention, the image and feature databases fora microplate include tables to hold image and feature data and a copy ofthe tables 116-142 (FIG. 7) excluding the manufacturer table 120 and thesystem table 138 used for the system database 92. In another embodimentof the present invention, the image and feature databases 94, 96, 98,100 include a copy or all of the tables 116-142 (FIG. 7). In anotherembodiment of the present invention, the image and feature databases 94,96, 98, 100 do not include a copy of the tables 116-142 (FIG. 7) usedfor the system database 92. However, having a copy of the systemdatabase 92 tables in the image and feature databases allows individualimage and feature databases to be archived and copied to another datastorage system for later review and thus aids analysis.

The image and feature databases 94, 96, 98, 100, tables 144 include awell field table 146 for storing information about fields in a well. Thewell field table 146 is linked to a well feature table 148 that includesinformation a list of features that will be collected from a well. Thewell field table 146 is also linked to a feature image table 150 thatincludes a list of images collected from a well and a cell table 152that includes information to be collected about a cell. The cell table152 is linked to a cell feature table 154 that includes a list offeatures that will be collected from a cell. However, more or fewertables can also be used, more or fewer links can be used to link thetables, and the present invention is not limited to the tables describedfor the image and feature databases.

Spooling Experimental Data

As was discussed above, the analysis instruments modules 12, 14, 16generate a large amount of data including image data, feature data, andsummary data for sub-containers and containers. The raw feature datavalues are stored as database files with multiple tables described above(e.g., FIG. 8). To prevent analysis instruments 12, 14, 16 and/or thestore clients 18, 20, 22 from running out of file space, database filesare managed using a hierarchical data management system.

FIG. 9 is a flow diagram illustrating a Method 156 for spoolingexperimental data. At Step 158, a second database is copied from ananalysis instrument to a shared database. The second database includesconfiguration data used to collect data from a container, summary datafor the container calculated from one or more sub-containers in thecontainer and summary data for sub-containers in the containercalculated from image data and feature data collected from desiredsub-containers. The data in the second database is organized into one ormore database tables. At Step 160, multiple third databases are copiedto a shared database file server. The multiple third databases includeimage data and a feature data collected from the desired sub-containersin the container. The data in the third database is organized into oneor more database tables. At Step 162, a location of the second databaseand the one or more third databases is updated in a first database onthe analysis instrument to reflect new storage locations for the seconddatabase on the shared database and one or more third databases on theshared database file server. The first database includes links to thesecond database and the one or more third databases but does not includeany data collected from the container. The first database is used by adisplay application to view data collected from a container.

In another preferred embodiment of the present invention, Method 156further comprises copying the first database from the analysisinstruments 12, 14, 16 to a store client computers 18, 20, 22. Such anembodiment allows a display application on the store client computers18, 20, 22 to view the data collected from the container using the firstdatabase copied to local storage on the client computers 18, 20, 22.

In another preferred embodiment of the present invention, Method 156further comprises locating the first database on the analysisinstruments 12, 14, 16 from store client computers 18, 20, 22. Such anembodiment allows a display application on the store client computers18, 20, 22 to view the data collected from the container at a remotelocation on the exemplary data storage system 10′ from the store clientcomputers 18, 20, 22.

The data collected is viewed from the display application on the storeclient computers 18, 20, 22 by retrieving container and sub-containerdata from the second database on the shared database 24 and image andfeature data from the multiple third databases on the shared databasefile server 28.

In one exemplary preferred embodiment of the present invention, at Step158, a system database 92 (FIG. 5) is copied from an analysis instrument12, 14, 16 to the shared database 24. The system database 92 includesconfiguration data used to collect data from a microplate, summary datafor the microplate calculated from one or more wells in the microplate(e.g., Table 3) and summary data for wells in the microplate (e.g.,Table 2) calculated from image data and feature data (e.g., Table 1)collected from desired wells as was described above. The data in thesystem database 92 is organized into one or more database tables (e.g.,FIG. 7).

At Step 160, one or more image and feature databases 94, 96, 98, 100 arecopied to the shared database file server 28. The one or more image andfeature databases 94, 96, 98, 100 include image data and a feature datacollected from the desired wells in the microplate. The data in the oneor more image and feature databases is organized into one or moredatabase tables (e.g., FIG. 8).

At Step 162, a location of the system database 92 and the one or moreimage and feature databases 94, 96, 98, 100 is updated in an applicationdatabase 90 (FIG. 6) on the analysis instrument 12, 14, 16 to reflectnew storage locations for the system database 92 on the store database24 and one or more image and feature databases 94, 96, 98, 100 on thestore archive 28.

In one preferred embodiment of the present invention, the applicationdatabase 90 is a pass-through database that includes links (e.g., FIG.6) to the system database 92 and the one or more image and featuredatabases 94, 96, 98, 100 but does not include any data collected fromthe microplate. In another embodiment of the present invention, theapplication database 90 includes data from the microplate. Theapplication database 92 is used by a display application to view datacollected from a microplate. However, the present invention is notlimited to this embodiment and other containers, sub-containers, (e.g.,bio-chips with multiple micro-gels) and databases can also be used.

Hierarchical Management of Experimental Data

FIG. 10 is a flow diagram illustrating a Method 164 for hierarchicalmanagement of experimental data. At Step 166, a hierarchical storagemanager is initialized with a pre-determined storage removal policy. AtStep 168, the hierarchical storage manager applies the pre-determinedstorage removal policy to database files in a database. At Step 170, atest is conducted to determine whether any database files on thedatabase match the pre-determined storage removal policy. If anydatabase files in the database match the pre-determined storage removalpolicy, at Step 172, the database files are copied from the database toa layer in a hierarchical store management system. At Step 174, databasefiles in the database are replaced with placeholder files. Theplaceholder files include links to the actual database files copied tothe layer in the hierarchical store management system. If no databasefiles in the database match the pre-determined storage removal policy,at Step 176, no database files are copied from the database to a layerin a hierarchical store management system.

In one exemplary preferred embodiment of the present invention, thepre-determined storage removal policy includes one or more rulesillustrated by Table 4. However, more or fewer storage removal policyrules can also be used and the present invention is not limited tostorage removal policy rules illustrated in Table 4.

TABLE 4 PERCENTAGE OF DISK SPACE AVAILABLE OR PERCENTAGE OF DISK SPACEUSED. NUMBER OF FILES. DATE A FILE IS STORED. SIZE OF A FILE. NUMBER OFDAYS SINCE A FILE WAS LAST ACCESSED. FILE TYPE. FILE NAME.

Method 164 includes HSM steps that provide a method to allow on-lineaccess to virtually unlimited amounts of “virtual” disk space on datastorage system 10′. The virtual disk space is provided with amulti-layer hierarchical storage management system. The virtual diskspace is provided without changing the layout of any database and is“invisible” to a user.

In one exemplary preferred embodiment of the present invention, the HSMsteps of Method 164 provide an archival method that implements athree-layer storage hierarchy including the disk archive 32, the opticaljukebox 34 and the tape drive 36. However, more or fewer layers ofstorage can also be used and the present invention is not limited to HSMtechniques with three-layer storage. Additional storage layers in thestorage hierarchy are added as needed without changing the layout of anydatabase or the functionality of the hierarchical storage manager. Thehierarchical storage manager can copy database files to layers in anN-Layer storage hierarchy without modification.

In addition, virtually unlimited amounts of “virtual” disk space can beprovided with a three-layer hierarchical storage management system byperiodically removing re-writeable optical disks, from the opticaljukebox 34 and tapes from the tape drive 36 when these storage mediumsare filled with data. The re-writeable optical disks and tapes arestored in a data library for later access. In another preferredembodiment of the present invention, the data library is directlyaccessible from computer network 40.

In a preferred embodiment of the present invention, Method 164 supportsat least two modes of database file archiving. However, more or fewermodes of database archiving can also be used and the present inventionis not limited to the two modes described.

In the first mode, the store server 26 retains database files onindividual analysis instruments 12, 14, 16, where they were originallygenerated. The store server 26 uses Method 164 to automatically managethe free space on the analysis instrument 12, 14, 16 disks to move filesinto a layer in the three-tiered storage management system. To the enduser the files will appear to be in the same directories where they wereoriginally stored. However, the files may actually be stored on the diskarchive 32, the optical jukebox 34, or in a Digital Linear Tape (“DLT”)36 library.

In the second mode, the store server 26 spools database files from theanalysis instruments 12, 14, 16, to the shared database 24 and theshared database file server 30 (e.g., using Method 156). The storeserver's 26 in turn manages database files on the shared database fileserver 30 using Method 164. In the second mode, the files may also bestored on the disk archive 32, the optical jukebox 34, or in a DLT 36library.

Experimental Data Presentation

As was discussed above, an analysis instrument 12, 14, 16 can generate ahuge amount of experimental data. To be useful, the experimental datahas to be visually presented to a scientist or technician for analysis.

FIG. 11 is a flow diagram illustrating a Method 178 for presentingexperimental data. At Step 180, a list including one or more containersis displayed using a first database from a display application on acomputer. The containers include multiple sub-containers. Image data andfeature data was collected from the one or more containers. The firstdatabase is a pass-through database including links to other databaseswith experimental data. At Step 182, a first selection input is receivedon the display application for a first container from the list. At Step184, a second database is obtained for the first container from a firstremote storage location. The first remote location is remote to thecomputer running the display application. The second database includesconfiguration data used to collect data from the first container,summary data for the first container calculated from the sub-containersin the first container and summary data for desired sub-containers inthe first container calculated from image data and feature datacollected from desired sub-containers. At Step 186, a second selectioninput is received on the display application for one or moresub-containers in the first container. At Step 188, multiple thirddatabases are obtained from a second remote storage location. Themultiple third databases include image data and feature data collectedfrom the one or more sub-containers in the first container. At Step 190,a graphical display is created from the display application includingcontainer and sub-container data from the second database, image dataand feature data from the multiple third databases collected from theone or more sub-containers. Data displayed on the graphical display willappear to be obtained from local storage on the computer instead of thefirst remote storage location and the second remote storage location.

In one exemplary preferred embodiment of the present invention, Method178 is used for displaying experimental data collected from microplateswith multiple wells. However, the present invention is not limited tothis embodiment and can be used for other containers and sub-containersbesides microplates with multiple wells (e.g., bio-chips with multiplemicro-gels).

In such an exemplary embodiment at Step 180, a list including multiplemicroplates is displayed from a display application on a computer. Themicroplates include multiple wells. Cell image data and cell featuredata were collected from the multiple microplates. The displayapplication uses an application database 90 to locate other databases,including experimental data.

In one preferred exemplary embodiment of the present invention, theapplication database 90 is located on the exemplary data storage system10′ at a location remote from the computer including the displayapplication. The application database 90 is used from the computerincluding the display application without copying the applicationdatabase 90 from a remote location on the exemplary data storage system10′.

In another exemplary preferred embodiment of the present invention, theapplication database 90 is copied from a location on the exemplary datastorage system 10′ to local storage on the computer including thedisplay application. In such an embodiment, the application database 90is copied to, and exists on the computer including the displayapplication.

At Step 182, a first selection input is received on the displayapplication for a first microplate from the list. At Step 184, a systemdatabase 92 is obtained for the first microplate from a first remotestorage location. The first remote storage location is remote to thecomputer running the display application. The system database 92includes configuration data used to collect data from the firstmicroplate summary data for the first microplate calculated from thewells in the first microplate and summary data for desired wells in thefirst microplate calculated from image data and feature data collectedfrom desired wells.

At Step 186, a second selection input is received on the displayapplication for one or more wells in the first microplate. At Step 188,multiple image and feature databases 94, 96, 98, 100 are obtained from asecond remote storage location. The multiple image and feature databases94, 96, 98, 100 include image data and feature data collected from theone or more wells in the first microplate. At Step 190, a graphicaldisplay is created from the display application including microplate andwell summary data from the system database 92, image data and featuredata from the multiple image and feature databases 94, 96, 98, 100collected from the one or more wells. Data displayed on the graphicaldisplay appears to be obtained from local storage on the computerinstead of the first remote storage location and the second remotestorage location.

FIG. 12 is a block diagram illustrating an exemplary screen display 192for visually displaying experimental data from a display application.The screen display 192 includes a display of multiple sub-containers 194in a container 196. The container 194 includes 384 sub-containers(numbers 1-24×letters A-P or 24×16=384). The screen display 192 alsoincludes container summary data 198, sub-container summary data 200,image data 202, and feature data 204. The screen display 192 is capableof displaying the data in both graphical formats and textual formatsdepending on user preferences. A user can select his/her displaypreferences from menus created by the display application (Notillustrated in FIG. 12). Screen display 192 illustrates exemplary datafor sub-container A-3 illustrated by the blacked sub-container 206 inthe container 196. Experimental data collected from a container isvisually presented to a scientist or lab technician for analysis usingMethod 178 and screen display 192 with a pass-through database withmultiple links to multiple databases from multiple remote locations.

In one exemplary preferred embodiment of the present invention, a StoreApplication Programming Interface (“API”) is provided to access and usethe methods and system described herein. As is known in the art, an APIis set of interface routines used by an application program to access aset of functions that perform a desired task.

In one specific exemplary preferred embodiment of the present invention,the store API is stored in a Dynamic Link Library (“DLL”) used with theWindows 95/98/NT/2000 operating system by Microsoft. The DLL is called“mvPlateData.DLL.” However, the present invention is not limited tostoring an API in a Window's DLL or using the described name of the DLLand other methods and names can also be used to store and use the API.As is known in the art, a DLL is library that allows executable routinesto be stored and to be loaded only when needed by an application. TheStore API in a DLL is registered with the Window's “REGSVR32.EXE”application to make it available to other applications. The Store APIprovides an interface access to plate, well image and cell featureinformation and provides a facility to enter desired well featureinformation that will be collected.

These methods and system described herein may allow experimental datafrom high-throughput data collection/analysis systems to be efficientlycollected, stored, managed and displayed. The methods and system can beused for, but is not limited to storing managing and displaying cellimage data and cell feature data collected from microplates includingmultiple wells or bio-chips including multiple micro-gels in which anexperimental compound has been applied to a population of cells. Ifbio-chips are used, any references to microplates herein, can bereplaced with bio-chips, and references to wells in a microplate can bereplaced with micro-gels on a bio-chip and used with the methods andsystem described.

The methods and system may provide a flexible and scalable repository ofcell data that can be easily managed and allows cell data to beanalyzed, manipulated and archived. The methods and system may improvethe identification, selection, validation and screening of newexperimental compounds which have been applied to populations of cells.The methods and system may also be used to provide new bioinformatictechniques used to make observations about cell data.

It should be understood that the programs, processes, methods andsystems described herein are not related or limited to any particulartype of computer or network system (hardware or software), unlessindicated otherwise. Various types of general purpose or specializedcomputer systems may be used with or perform operations in accordancewith the teachings described herein.

In view of the wide variety of embodiments to which the principles ofthe present invention can be applied, it should be understood that theillustrated embodiments are exemplary only, and should not be taken aslimiting the scope of the present invention.

For example, the steps of the flow diagrams may be taken in sequencesother than those described, and more or fewer elements may be used inthe block diagrams. While various elements of the preferred embodimentshave been described as being implemented in software, in otherembodiments in hardware or firmware implementations may alternatively beused, and vice-versa.

The claims should not be read as limited to the described order orelements unless stated to that effect. Therefore, all embodiments thatcome within the scope and spirit of the following claims and equivalentsthereto are claimed as the invention.

1. A method for spooling experimental data on a computer system, themethod comprising the steps of: copying a second database from ananalysis instrument to a shared database, wherein the second databaseincludes configuration data used to collect data from a container,summary data for the container calculated from a plurality ofsub-containers in the container and summary data for sub-containers inthe container calculated from a plurality of image data and plurality offeature data collected from desired sub-containers, and wherein the datain the second database is organized into a plurality of database tables;copying a plurality of third databases from an analysis instrument to ashared database file server, wherein the plurality of third databasesinclude a plurality of image data and a plurality of feature datacollected from the plurality of sub-containers in the container, andwherein the data is organized in a plurality of database tables; andupdating the location of the second database and the plurality of thirddatabases in a first database on the analysis instrument to reflect newstorage locations for the second database on the shared database and theplurality of third databases on the shared database file server, whereinthe first database is a pass-through database that includes links to thesecond database and plurality of third databases but does not includeany data collected from the container, and wherein the first database isused by a display application to view data collected from a container.2. A computer readable medium having stored therein instructions forcausing a central processing unit to execute instructions for the methodof claim
 1. 3. The method of claim 1 further comprising: copying thefirst database from the analysis instrument to a local storage locationon a store client computer to allow a display application on the storeclient computer to view the data collected from the container; andviewing the data collected from the display application on the storeclient computer by using the first database to retrieve container andsub-container data from the second database on the shared database andimage and feature data from the plurality of third databases on theshared database file server.
 4. The method of claim 1 furthercomprising: locating the first database from a store client computer ata remote location to allow a display application on the store clientcomputer to view the data collected from the container; and viewing thedata collected from the display application on the store client computerby using the first database at the remote location to retrieve containerand sub-container data from the second database on the shared databaseand image and feature data from the plurality of third databases on theshared database file server.
 5. The method of claim 1, wherein thecontainer includes a microplate, and the plurality of sub-containersincluded wells in the microplate.
 6. The method of claim 1, wherein thecontainer includes a bio-chip and the plurality of sub-containersinclude selected micro-gels on the bio-chip.
 7. The method of claim 1,wherein the plurality of sub-containers include a plurality of cellstreated with an experimental compound.
 8. The method of claim 1, whereinthe shared database includes faster access local storage.
 9. The methodof claim 1, wherein the shared database file server includes sloweraccess remote storage.